Payment management method and system using an IC card

ABSTRACT

A payment management method and system for performing suitable payment management, wherein a user of a credit IC card can store a transaction history in the IC card, can collate the transaction history with charged amount data possessed by a credit company, can quickly confirm a payment due date, can judge an illegal demand for purchase done by the non-authorized user, and can know charged amounts claimed for the next time. The system includes the IC card having a storage means for storing the transaction history data therein, a terminal device for accessing the data within the IC card, and a server of the credit company connected to the terminal device via a network for storing storage means for storing credit user data demanded by a credit member store therein. The terminal device stores transaction history data at the time of a purchase with use of the IC card in the credit member store into the IC card, extracts the credit user data from the server of the credit company, and collates the transaction history data read out from the IC card with the credit user data extracted from the server. The terminal device displays its collated result is displayed thereon.

BACKGROUND OF THE INVENTION

[0001] The present invention relates to a payment management method andsystem which suitably use a credit card based on an intelligent card(which will also be referred to as IC card, hereinafter).

[0002] Conventionally, a user of a credit card, after using it, haschecked a customer copy or receipt of the card received from one ofcredit member stores of the credit card against a debit note deliveredfrom a credit company, and has judged the transaction history to becharged next time or after the next time and a wrong demand. Further,the user copy of the credit is disclosed in Japanese Patent ApplicationNO. 7-85086 (JP-A-8-287201) a method for storing a transaction historyin a storage in an IC card.

[0003] In the above method, the card user cannot know an amount claimedto be drawn next time before he accepts the bill from the card company.If the user lost the user copy, then he cannot know when and how much heused it and also cannot know an illegal use (if any) and an amount to bedemanded after the next time because he cannot know contents of thedebit note.

[0004] As means for solving such problems, there is already known such aservice that a user can collate his amount claimed per month throughtelephone or Internet.

[0005] In the aforementioned claimed-amount collation service, however,the user searches for his transaction history stored in the cardcompany, so it takes the user lots of time to input his card number andafter the searching, he must troublesomely check a copy or as a receiptreceived upon its use against the transaction history. Even when theuser such service, it takes lots of time to register his transactionhistory after the card company receives the transaction history from acredit card member store, for which reason the user may sometimes failsto find his transaction history by searching for it based on the aboveservice.

SUMMARY OF THE INVENTION

[0006] It is therefore an object of the present invention to provide apayment management method and system which can solve the above problemsin the prior art and wherein a transaction history is stored in an ICcard so that a user of the IC credit card can collate the transactionhistory with demanded amount data possessed by a card company, canquickly confirm a demanded amount date, and can grasp payment dueamounts claimed next time and after the next time to thereby realizesuitable payment management.

[0007] In an aspect of the present invention, the above object isattained by a payment management method in a system which includes an ICcard having a storage means for storing transaction history datatherein, a terminal device for accessing the data within the IC card,and a server in a card company connected with the terminal device via anetwork and having a storage means for storage of credit user datademanded by a credit card member store. The payment management methodincludes steps of storing into the storage means within the IC card thetransaction history data when the user paid in the credit member storewith use of the IC card, reading out the transaction history data fromthe IC card with use of the terminal device, reading out the credit userdata from the server storage means with use of the terminal device,collating the transaction history data read out from the IC card withthe credit user data read out from the server, and displaying itscollated result on the terminal device.

[0008] The step of displaying the collated result may include a step ofdisplaying the collated result as divided into a charged amount claimednext time and an charged amount claimed after the next time.

[0009] The transaction history data within the IC card and the credituser data within the server may include demand date data indicative of adate on which the card user is to be demanded and payment state dataindicative of whether or not the payment is finished, such that thedemand date data and payment state data of the transaction history datawithin the IC card can be updated according to the credit user data ofthe server extracted by the terminal device.

[0010] Upon collation, when the transaction history data is present inthe storage means of the IC card but the credit demand datacorresponding to the transaction history data is not present in thestorage device connected to the server, data indicative of ‘notdemanded’ may be added to the transaction history data and its collatedresult may be displayed. Upon collation, further, when the credit demanddata is present in the storage device connected to the server but thetransaction history data corresponding to the credit demand data is notpresent in the storage means of the IC card, the transaction historydata corresponding to the credit demand data may be newly added to thestorage device of the IC card, data indicative of ‘unknown billing data’may be added to the added transaction history data, and its collationresult may be displayed.

[0011] The payment management method of the present invention mayfurther include a step of displaying at least the transaction historydata of already paid or of unknown demand in the transaction historydata of the storage means of the IC card by means of the terminaldevice, and deleting these transaction history data.

[0012] The payment management method of the present invention mayfurther include a step of issuing an inquiry relating to the transactionhistory data of the unknown demand to the credit company by the user whogive an instruction on a display screen showing the collated result.

[0013] In another aspect of the present invention, there is provided apayment management method in a system which includes an IC card having astorage means for storing transaction history data therein, a terminaldevice for accessing the data within the IC card, and a server of acredit company having storage means connected to the terminal device viaa network for storing credit user data demanded by a credit memberstore. The payment management method includes steps of storing into thestorage means of the IC card the transaction history data when a carduser paid in the credit member store with use of the IC card, readingout the transaction history data from the IC card by means of theterminal device, transmitting the credit user data from the server ofthe credit company to the terminal device, receiving the transmittedcredit user data at the terminal device, collating the transactionhistory data read out from the IC card with the received credit userdata, and displaying its collated result on the terminal device.

[0014] The step of reading out the transaction history data from the ICcard by means of the terminal device may include a step of storing theread transaction history data into the storage means of the terminaldevice; and the step of collating the transaction history data read outfrom the IC card at the terminal device with the credit user dataextracted from the server may collate the transaction history datastored in the storage means of the terminal device with the credit userdata extracted from the server.

[0015] In a further aspect of the present invention, there is provided apayment management system which uses an IC card having therein a storagemeans for storage of transaction history data to manage payment datarelating to user's payment conducted in a credit member store. Thepayment management system includes a means for reading out thetransaction history data from the IC card, a means for acquiring thecredit user data from the server of the credit company for management ofthe credit user data about payment based on the IC card, a means forcollating the transaction history data read out from the IC card withthe acquired credit user data to create a collated result, and means fordisplaying the created collated result.

[0016] The IC card in the present invention, which is used for creditpurchase in the credit member store, has a communication device and astorage device for holding the transaction history data obtained throughthe communication device therein, the data containing the name of themember store used at the time of the credit purchase and a purchasedamount therefor.

[0017] A processor also included in the IC card compares own credit dataobtained through the communication device and network with theaforementioned transaction history data, and when a record differentfrom the history data is present in the credit data, records thedifferent record in the storage device as the transaction history data.

[0018] Also included in the transaction history data are data on apayment due date for the transaction or purchased amount and dataindicative of a payment state for the purchased amount.

[0019] Further, a program for use in the terminal device in the presentinvention is provided as fixed to a recording medium which follows. Thatis, there is provided a recording medium for holding therein anexecutable program read into a terminal device which can be connected toanother storage device via a network to read and write data from and toan IC card used as a credit card. The program includes steps of storingtransaction history data when a user of the IC card used it in a creditmember store for his payment into a storage means within the IC card,reading out the transaction history data from the IC card, extractingcredit user data about the IC card being stored in the storage devicevia the network from the storage device, collating the transactionhistory data read out from the IC card with the credit user data, anddisplaying its collated result on the terminal device.

[0020] If some piece of data is present not in the transaction historydata but present in the credit user data in the collating step, anaddition of the third data to the transaction history data is displayedin the displaying step.

BRIEF DESCRIPTION OF THE DRAWINGS

[0021]FIG. 1 is a block diagram of an arrangement of a paymentmanagement system in accordance with an embodiment of the presentinvention, including an IC card;

[0022]FIG. 2 shows an exemplary transaction history table stored in astorage device within an IC card;

[0023]FIG. 3 shows another exemplary transaction history table stored inthe storage device of the IC card;

[0024]FIG. 4 shows a further exemplary transaction history table storedin the storage device of the IC card;

[0025]FIG. 5 is an exemplary display screen showing a result ofcollation of the transaction history table within the IC card withdemanded amount data stored in a storage device of a card companysystem;

[0026]FIG. 6 is an exemplary display screen showing a result of thetransaction history table after read out from the IC card;

[0027]FIG. 7 is a flowchart showing a procedure of operations when auser of the IC card collates the transaction history table of the ICcard with the demand amount data of the card company;

[0028]FIG. 8 is a flowchart showing a procedure of operations when theuser wants to deletes a record of the transaction history table storedin the storage device of the IC card; and

[0029]FIG. 9 shows an example of the demanded amount data stored in thestorage device connected to a server of the card company.

DESCRIPTION OF THE EMBODIMENTS

[0030] Explanation will first be made as to reference numerals used inembodiments of the present invention.

[0031] Reference numeral 101 denotes a card processor, numeral 102denotes an input device, 103 a processor, 104 an IC card read/writedevice, 105 a display device, 106 a communication device, 107 a storagedevice, 120 an IC card, 121 a communication device, 122 a processor, 123a storage device, 110 a card company system, 111 a communication device,112 a card company server, 113 a storage device, 141 an IC cardprocessor, 142 an input device, 143 a processor, 144 an IC cardread/write device, 145 a display device, 146 a communication device, 147a storage device, 130 a network.

[0032] Embodiments of the present invention will be explained in detailwith reference to accompanying drawings.

[0033]FIG. 1 is a block diagram of an arrangement of a paymentmanagement system in accordance with an embodiment of the presentinvention, including an IC card 120. The system includes a cardprocessor 101 installed in a credit member store for reading and writingdata within the IC card, an input device 102, a processor 103, an ICcard read/write device 104, a display device 105, a communication device106 and a storage device 107. The IC card 120 includes a communicationdevice 121, a processor 122 and a storage device 123. A card companysystem 110 for providing demanded amount data possessed by a cardcompany to users, includes a communication device 111, a card companyserver 11 and a storage device 113. An IC card processor 141 for readingand writing data within the IC card, is used by credit card users. TheIC card processor 141 includes an input device 142, a processor 143, anIC card read/write device 144, a display device 145, a communicationdevice 146 and a storage device 147. A network 130 is used forcommunication with the card processor 101, card company system 110 andIC card processor 141 for use by the users.

[0034]FIG. 2 is an example of a transaction history table stored in thestorage device 123 of the IC card 120, which shows a transaction history201 indicative of a purchased or charged amount, transaction or purchasedate and transaction or purchase store, payment due date data 202indicative of a demanded date (timing of debiting user's bank account)for the purchased amount, payment state data 203 indicative of a stateof paid or unpaid (debited or not debited), other data 204 indicative ofother user data, and user sequence number (ID (identifier) of thetransaction history) 205.

[0035]FIG. 3 is an example of a transaction history table updated afterthe transaction history table stored in the storage device 123 of the ICcard 120 is collated with the demanded amount data stored in the storagedevice 113 connected to the card company server 112 of the creditcompany. The updated table shows a transaction history 301 indicative ofa purchased amount, purchase date and purchase store, payment due datedata 302 indicative of a date of payment for the purchased amount,payment state data 303 indicative of a state of paid or not paid, otherdata 304 indicative of other user data, and a user sequence number 305.

[0036]FIG. 4 is an example of the transaction history table within theIC card 120 after ‘paid’ items of the payment state data in thetransaction history table of FIG. 3 are deleted and then the table isupdated. The updated table shows a transaction history 401 indicative ofa purchased amount, purchase date and purchase store, payment due datedata 402 indicative of a date of payment for the purchased amount,payment state data 403 indicative of a state of paid or not paid, otherdata 404 indicative of other user data, and a user sequence number 405.

[0037]FIG. 5 is an example of a display screen showing a result ofcollation of the transaction history table within the IC card 120 withdemand data stored in the storage device 113 of the card company system,in which reference numeral 501 denotes a transaction history alreadypaid, numeral 502 denotes an amount to be paid next time, 503 denotes anamount to be paid after the next time, 504 denotes a unknownuser-demanded amount (unknown demand) which is included in the demanddata in the storage device 113 and is not present in the transactionhistory table within the IC card 120, 505 and 506 denote buttons 505 and506 used when the user wants to inquire the unknown demand of the creditcompany respectively.

[0038]FIG. 6 is an example of a display screen showing a result afterthe transaction history table within the IC card 120 is read outoffline, in which reference numeral 601 denotes a transaction historyalready paid, numeral 602 denotes an amount to be paid next time, 603denotes an amount to be paid after the next time, 604 denotes a unknownuser-demanded amount (unknown demand), 605 and 606 denote buttons 605and 606 used when the user instructs to delete the unknown demand andpaid history in the transaction history table of the IC card 120 fromthe transaction history table respectively.

[0039]FIG. 9 is an example of demand data (credit purchase data) storedin the storage device 113 connected to the card company server 112, inwhich reference numeral 901 denotes a transaction history indicative ofa purchased amount, purchase date and purchase store, numeral 902denotes payment due date data indicative of a date of payment for thepurchased amount, 903 denotes payment state data indicative of a stateof paid or not paid, and 905 denotes a user sequence number.

[0040]FIG. 7 is a flowchart showing a procedure of operations when theuser collates the transaction history table of the IC card with thecharged amount data of the credit company in the system of the presentembodiment.

[0041] When the card user first buys and pays for it with the IC card120 in the credit member store, the card member store writes thetransaction history 201, payment due date data 202, other data 204 anduser sequence number 205 into the storage device 123 of the IC card 120with use of the card processor 101 (step 700). At this time, ‘not paid’indicative of ‘unpaid’ is written into the payment state data 203 of thetransaction history item. Further, ‘temporary’ payment due date as anexpectancy is written into the payment due date data 202. The‘(temporary)’ in the payment due date (temporary) in FIG. 2 means thepayment due date is temporary. These data generated in the credit memberstore are transmitted as charged amount data to the card company system110 from the card processor 101. In the card company system 110, thesedata are written in the storage device 113 as shown in FIG. 9. In thisconnection, since a payment due date can be determined for the receiveddata in the card company system 110, the determined data is written asthe payment due date data 902.

[0042] After the operation of the step 700 upon payment in the creditmember store, the card user can confirm and rearrange the contents ofthe IC card 120 and also can collate it with data of the card company. Aflow of such operations in the IC card processor 141 is shown by steps701 to 708. Some of credit member stores may be not installed with suchan card processor 101. When the card user buy and pays for it with hiscard in such a store, the user himself can look at his customer copy orreceipt and can conduct the operation (writing of data into the IC card120) of the step 700 using the IC card processor 141.

[0043] Next, when the card holder inserts the IC card 120 into the ICcard processor 141 and then conducts a predetermined operation, the ICcard processor 141 reads out the transaction history 201, payment duedate data 202, payment state data 203, other data 204 and user sequencenumber 205 (FIG. 2) as well as the card number (credit number)previously registered in the IC card 120, from the storage device 123 ofthe inserted IC card 120 (step 701). The card number is an identifierfor identifying the IC card 120.

[0044] The IC card processor 141 then communicates via its communicationdevice 146 and network 130 with the credit company to judge whether ornot the card number of the IC card is one of numbers of credit cardsissued from the credit company on the basis of data stored in thestorage device 113 of the credit company. When the IC card processor 141confirms that the card number is confirmed as one of numbers of thecredit cards issued from the credit company, the processor proceeds tothe next step 703, whereas, when determining that the card number is notone of numbers of the issued credit cards, the processor terminates itsoperation (step 702).

[0045] Subsequently the IC card processor 141 searches the storagedevice 113 having company demand data stored therein for a chargedamount data (FIG. 9) corresponding to the corresponding card number andextracts from the storage device 113 the associated transaction history901, payment due date data 902, payment state data 903 and user sequencenumber 905 (step 703).

[0046] The IC card processor 141 compares the data within the IC card120 read out at the step 701 with the associated data of the cardcompany for each user number (step 704), and updates the transactionhistory table (FIG. 2) within the IC card 120 (step 705), which will bedetailed below.

[0047] First of all, when the user sequence number 205 read out at thestep 701 has the same record as in the user sequence number 905extracted at the step 703, the IC card processor 141 compares the userhistories 201 and 901 for the same user sequence number record; whereas,when the user sequence numbers fail to have the same record, the IC cardprocessor 141 writes data indicative of the fact that the user historiesare different in the other data 204. Next, the payment due date data 202and 902 are compared for the same user sequence number so that adifference therebetween causes the contents of the payment due date data902 to be written into the payment due date data 202. The payment statedata 203 and 903 are then compared so that a difference therebetweencauses the contents of the payment state data 903 to be written into thepayment state data 203. A user sequence number present not in the usersequence number 205 of the transaction history table within the IC card120 is present in the user sequence number 905 of the record extractedat the step 703, the transaction history 901, payment due date data 902,payment state data 903 and user sequence number 905 of the user sequencenumber are written as a new record into the associated transactionhistory 201, payment due date data 202, payment state data 203 and usersequence number 205 in the transaction history table of the IC card 120.Further ‘unknown demand (not inquired)’ is written into the other data204. An example of results thus written and updated is shown in FIG. 3.When there is one of the user sequence numbers read out at the step 701which is not present in the user sequence number 905 of the recordextracted from the server at the step 703, ‘not demanded’ is writteninto the other data 204 of the associated record of the transactionhistory table within the IC card 120.

[0048] The IC card processor 141 calculates a total sum amount from theresults of the collation and updating at the steps 704 and 705, displaysthe resultant sum amount on the display device 145 of the IC cardprocessor 141, and stores the collated result in the storage device 147of the IC card processor 141 (step 706). FIG. 5 shows an exemplarydisplay screen of the collated transaction history result.

[0049] In the display screen (FIG. 5) of the collated transactionhistory result, next, when the user wants to inquire the unknown demandor charge of the card company, the user pushes the YES button 505 fromthe input device 142 of the IC card processor 141 (step 707). Pushing ofthe YES button 505 causes the user sequence number (user sequence number5 in the example of FIG. 5) of the unknown demand to be transmitted fromthe communication device 146 of the IC card processor 141 via thenetwork 130 to the credit company. Thereafter the IC card processor 141updates the other data 204 of the transaction history table stored inthe storage device 123 of the IC card 120 to ‘unknown demand (alreadyinquired)’ (step 708), thus terminating its operation. When the userdoes not want to inquire the unknown demand of the credit company andthus when he pushes the NO button 505 from the input device 142 of theIC card processor 141 (step 707), this causes the IC card processor 141to terminate its operation. In this connection, a similar operation maybe realized not only for the ‘unknown demand’ but also ‘not demanded’.

[0050]FIG. 8 is a flowchart showing a procedure of operations when theuser wants to delete a record of the transaction history table stored inthe storage device 123 of the IC card 120 in the system of the presentembodiment. The operation of the flowchart starts with cardholder'sinsertion of the IC card 120 into the IC card processor 141 to performpredetermined operations.

[0051] First of all, the IC card processor 141 reads out the transactionhistory table from the storage device 123 of the IC card 120 (step 801).It is now assumed that the IC card processor 141 read out such atransaction history table as shown in FIG. 3.

[0052] The IC card processor 141 then searches the read-out transactionhistory table for a record of the payment state data 303 written as‘paid’ or a record of the other data 304 written as ‘unknown demand’(step 802). When failing to find such a record, the IC card processor141 terminates its operation. When finding a record of the ‘paid’ or‘unknown demand’, the IC card processor 141 displays the transactionhistory table read out at the step 801 on the display screen to inquirewhether to delete the record of the paid history or unknown demand ofthe card user. FIG. 6 is an exemplary display of the read-out result ofthe transaction history table in the case of presence of the paid orunknown demand record.

[0053] The card user pushes a YES button 605 or a NO button 606 on sucha display screen as shown in FIG. 6 (step 803). When the card user doesnot want to delete the paid history record nor the unknown demandrecord, the user pushes the NO button 606 from the input device 142 ofthe IC card processor 141, whereby the IC card processor 141 terminatesits operation. When the card user wants to delete the paid historyrecord or unknown demand record, the user pushes the YES button 605 fromthe input device 142 of the IC card processor 141 and selects the recordto be deleted from the input device 142 (step 804), whereby the IC cardprocessor 141 deletes the selected record and stores an updatedtransaction history table into the storage device 123 of the IC card 120(step 805). FIG. 4 shows a state after the paid history record wasdeleted from the state of FIG. 3.

[0054] A modification of the foregoing embodiment will next beexplained. Although data for collation with the transaction historytable of FIG. 2 stored in the storage device 123 of the IC card 120 isstored in the storage device 113 connected to the card company server112 of the credit company in the foregoing embodiment of the presentinvention, the credit company may previously transmit, by means ofelectronic mail, the charged amount data and credit card number of FIG.9 stored in the storage device 113 connected to the server of the creditcompany may to an electronic mail address of the credit card user viathe communication device 111 and network 130 so that, after the IC cardprocessor 141 receives the charged amount data and credit card number ofFIG. 9 via the communication device 146, the IC card processor 141stores the charged amount data and credit card number of FIG. 9 into thestorage device 147 of the processor 141, whereby, as in the foregoingembodiment of the present invention, the credit card user can collatethe transaction history table and credit card number of FIG. 2 stored inthe storage device 123 of the IC card 120 with the charged amount dataand credit card number of FIG. 9 stored in the storage device 147 of theIC card processor 141.

[0055] A second modification of the foregoing embodiment will beexplained. Although the transaction history table of FIG. 2 stored inthe storage device 123 of the IC card 120 is collated with the chargedamount data of FIG. 9 stored in the storage device 113 connected to thecard company server 112 of the credit company in the foregoingembodiment, the IC card processor 141 may previously store thetransaction history table and credit card number of FIG. 2 stored in thestorage device 123 of the IC card 120 into the storage device 147 of theIC card processor 141, whereby, as in the foregoing embodiment, the usercan collate the transaction history table and credit card number of FIG.2 stored in the storage device 147 of the IC card processor 141 with thecharged amount data an credit card number of FIG. 9 stored in thestorage device 113 connected to the card company server 112 of thecredit company. Thereby, for example, the card user can take thefunction of the present invention into housekeeping software being usedby the card user to realize the aforementioned collation on thehousekeeping software.

[0056] A third modification of the foregoing embodiment will beexplained. When the IC card processor 141 has no function of updatingdata of the transaction history table within the storage device 123 ofthe IC card 120 in the foregoing embodiment, the transaction historytable of the storage device 123 of the IC card 120 may not be updated sothat, as in the foregoing embodiment, the transaction history table ofthe IC card 120 can be collated with the charged amount data of thestorage device 113 connected to the card company server 112, itscollated result may be displayed and be stored into the storage device147 of the IC card processor 141.

[0057] In accordance with the foregoing embodiment and itsmodifications, since the transaction history data relating to user's useis sequentially checked against the credit charged amount data possessedby the credit company, the card user can quickly know how much and whenthe user is charged by the credit company. Further, the user also canquickly know the charged amount data of the credit card actually used bythe user as well as wrongly-registered or illegally registered chargedamount data of the credit card. In addition, since deletion of thetransaction history data of ‘paid’ enables the storable capacity of theIC card to be kept at a suitable value, so that, when the user wants touse the credit card, he can write always new transaction history datainto the card in credit card member stores.

[0058] In accordance with the present invention, as has been explainedin the foregoing, since the transaction history data of the IC card isautomatically collated with the charged amount data possessed by thecredit company, the user of the credit card can quickly confirm itsdue-payment date, judge an undue charge for a purchase not actually doneby the user, and can know charged amount data to be paid after the nexttime.

What is claimed is:
 1. A payment management method in a system whichincludes an IC card having storage means for storing transaction historydata therein, a terminal device for accessing the data within the ICcard, and a server of a credit company having storage means connected tothe terminal device via a network for storing credit user data chargedby a credit member store, said method comprising the steps of: storingtransaction history data when a user of the IC card buys and pays for itwith the IC card, into the storage means of the IC card; reading outsaid transaction history data from said IC card with use of saidterminal device; extracting said credit user data from the storage meansof said server with use of said terminal device; collating thetransaction history data read out from said IC card with the credit userdata extracted from said server with use of said terminal device; anddisplaying a collated result on said terminal device.
 2. A paymentmanagement method as set forth in claim 1, wherein said step ofdisplaying the collated result includes a step of displaying thecollated result as divided into a charged amount claimed next time and acharged amount claimed after the next time.
 3. A payment managementmethod as set forth in claim 1, wherein he transaction history datawithin the IC card and the credit user data within the server mayinclude demand date data indicative of a date on which the card user isto be demanded and payment state data indicative of whether or not thepayment is finished, and the demand date data and payment state data ofthe transaction history data within the IC card are updated according tothe credit user data of said server extracted by said terminal device.4. A payment management method as set forth in claim 1, wherein, uponsaid collation, when the transaction history data is present in thestorage means of said IC card but the credit demand data correspondingto the transaction history data is not present in the storage deviceconnected to the server, data indicative of ‘not demanded’ is added tothe transaction history data and the collated result is displayed.
 5. Apayment management method as set forth in claim 1, wherein, upon thecollation, when the credit demand data is present in the storage deviceconnected to said server but the transaction history data correspondingto the credit demand data is not present in the storage means of the ICcard, the transaction history data corresponding to the credit demanddata is newly added to the storage device of the IC card, dataindicative of unknown demand may be added to the added transactionhistory data, and the collated result is displayed.
 6. A paymentmanagement method as set forth in claim 3, further including a step ofdisplaying at least the transaction history data of already paid or ofunknown demand in the transaction history data of the storage means ofthe IC card by means of the terminal device, and deleting thesetransaction history data.
 7. A payment management method as set forth inclaim 5, further including a step of displaying at least the transactionhistory data of already paid or of unknown demand in the transactionhistory data of the storage means of the IC card by means of theterminal device, and deleting these transaction history data.
 8. Apayment management method as set forth in claim 5, further including astep of issuing an inquiry relating to the transaction history data ofthe unknown demand to the credit company by the user who give aninstruction on a display screen showing the collated result.
 9. Apayment management method in a system which includes an IC card havingstorage means for storing transaction history data therein, a terminaldevice for accessing the data within the IC card, and a server of acredit company having storage means connected to the terminal device viaa network for storing therein credit user data demanded by a creditmember store, said method comprising the steps of: storing thetransaction history data when a card user paid with said IC card in thecredit member store, into the storage means of the IC card; reading outsaid transaction history data from said IC card by means of the terminaldevice; transmitting said credit user data from the server of the creditcompany to the terminal device; receiving said transmitted credit userdata at said terminal device; collating the transaction history dataread out from the IC card with the received credit user data; anddisplaying its collated result on the terminal device.
 10. A paymentmanagement method as set forth in claim 1, wherein said step of readingout the transaction history data from the IC card by means of theterminal device includes a step of storing the read-out transactionhistory data into the storage means of the terminal device; and saidstep of collating the transaction history data read out from the IC cardat the terminal device with the credit user data extracted from theserver includes a step of collating the transaction history data storedin the storage means of the terminal device with the credit user dataextracted from the server.
 11. A payment management method as set forthin claim 9, wherein said step of reading out the transaction historydata from the IC card by means of the terminal device includes a step ofstoring the read-out transaction history data into the storage means ofthe terminal device; and said step of collating the transaction historydata read out from the IC card at the terminal device with the credituser data extracted from the server includes a step of collating thetransaction history data stored in the storage means of the terminaldevice with the credit user data extracted from the server.
 12. Apayment management system which uses an IC card having therein storagemeans for storing transaction history data to manage payment datarelating to user's payment conducted in a credit member store, saidsystem comprising: means for reading out the transaction history datafrom said IC card means for acquiring the credit user data from theserver of the credit company for management of the credit user dataabout payment based on said IC card; means for collating the transactionhistory data read out from the IC card with the acquired credit userdata to create a collated result; and means for displaying the createdcollated result.
 13. An IC card which is used for credit purchase in acredit member store, and which has a communication device and a storagedevice for holding therein the transaction history data obtained throughsaid communication device, said data containing the name of the memberstore used at the time of the credit purchase and a purchased amounttherefor.
 14. An IC card as set forth in claim 13, said IC card has aprocessor, said processor compares own credit data obtained through acommunication device and a network with said transaction history data,and when a record different from the history data is present in creditdata, the processor records said different record in the recordingdevice as the transaction history data.
 15. An IC card as set forth inclaim 13, wherein said transaction history data include data on apayment due date for said purchased amount and data indicative of apayment state for the purchased amount.
 16. A recording medium forholding therein an executable program read into a terminal device whichcan be connected to another storage device via a network to read andwrite data from and to an IC card used as a credit card, said programcomprising the steps of: storing transaction history data when a user ofsaid IC card used it in a credit member store for his payment, into astorage means within said IC card; reading out said transaction historydata from said IC card; extracting credit user data about said IC cardbeing stored in the storage device via the network from said storagedevice; collating the transaction history data read out from said ICcard with said credit user data; and displaying a collated result on theterminal device.
 17. A recording medium as set forth in claim 16,wherein, when third data is present not in the transaction history databut present in the credit user data in said collating step, an additionof the third data to the transaction history data is displayed in saiddisplaying step.